Skip to content

wiki: the sub-3.12 install note said the opposite of what happened - #17

Merged
Jammy2211 merged 2 commits into
mainfrom
feature/sub-312-install-tombstone
Aug 19, 2026
Merged

wiki: the sub-3.12 install note said the opposite of what happened#17
Jammy2211 merged 2 commits into
mainfrom
feature/sub-312-install-tombstone

Conversation

@Jammy2211

Copy link
Copy Markdown
Contributor

Phase 2 of PyAutoLabs/PyAutoHands#238.

wiki/core/operations/installation.md told the assistant that every pre-2026.4.5.3 wheel was yanked, so pip install autogalaxy on 3.11 "fails with no matching distribution rather than silently resolving to an ancient version".

Silently resolving to an ancient version is exactly what it did. Verified on real 3.9/3.10/3.11 venvs against PyPI: all three installed the 2026.7.29.1 stack, exit 0, no JAX, no warning.

There is no such yank — 396 of 421 autolens releases are live, including the one sub-3.12 pip was landing on.

Corrected to: the real cut release (2026.7.29.2, not 2026.4.5.3), the real pre-fix behaviour, and the 2026.7.29.1.post1 tombstone that now refuses the install — including the --only-binary=:all: gap it cannot close. Explicit pins still resolve on old Pythons, as before.

🤖 Generated with Claude Code

Jammy2211 and others added 2 commits August 19, 2026 18:51
The installation page claimed pre-2026.4.5.3 wheels were yanked so that
`pip install autogalaxy` on 3.11 "fails with no matching distribution rather
than silently resolving to an ancient version". Silently resolving to an
ancient version is exactly what it did — verified on real 3.9/3.10/3.11 venvs.
No such yank exists: 396 of 421 autolens releases are live.

Corrected to the real cut release (2026.7.29.2), the real behaviour, and the
2026.7.29.1.post1 tombstone that now refuses the install, including the
--only-binary=:all: gap it cannot close.

Issue: PyAutoLabs/PyAutoHands#238

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
content_sha256 binds the prose to the page's pinned-commit claim, so editing
the body without re-stamping fails --check-provenance — which is the point.
Stamped with --write-provenance; --check-provenance is now 0 errors across all
41 wiki/core pages.

The 101 remaining warnings are the pre-existing "no git checkout resolvable"
class from running against a packaged install, not this change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Jammy2211 Jammy2211 changed the title wiki: the sub-3.12 install note said the opposite of what happened docs: correct the install page — wrong failure mode, wrong cut release, wrong support range Aug 19, 2026
@Jammy2211 Jammy2211 changed the title docs: correct the install page — wrong failure mode, wrong cut release, wrong support range wiki: the sub-3.12 install note said the opposite of what happened Aug 19, 2026
@Jammy2211
Jammy2211 merged commit 85f7e13 into main Aug 19, 2026
2 checks passed
@Jammy2211
Jammy2211 deleted the feature/sub-312-install-tombstone branch August 19, 2026 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant